Copyright: WOmenu Help File © 1994,95 Bremer Corp.


FALSEWOmenu Help File ¸ 1994,95 Bremer Corp.yesWOMENU&About~PopUpID(`WOMENU.HLP',`WOMENU.A__002')&Rights~PopUpID(`WOMENU.HLP',`WOMENU.R__002')noyesyesyesnonoWindows Office Menu Help06/06/95


Contents

(NOTE:  Users never see this Windows help file in User Mode.)

WOmenu Default Main Menu Picture

Introduction

Requirements

Quick Start

Users Windows Environment

Commands - Admin Mode

Commands - User Mode

Administration

Menu Items

Software Metering Service

Project Charging Service

WOmenu Utilities

Shareware


Run

Window Title Entry

Menu Rights

Item Title

Description

Program/Cmd

Work Directory

Window Title

Optional Rights

Insert Menu Item

Personal Menus

About

Ordering Information

Technical Support

Office Situation 1

Office Situation 2

DOSmenu Network Login Screen

DOSmenu Main Menu Screen

DOSmenu Main Help Screen

DOSmenu Workstation Status Screen

Interface Options

Network Options

Support File Options

All Rights

User Rights

Node Rights

Server Rights

Group Rights

Directory Rights

Group Rights (Faked)

File Rights

Environment Rights

Map Rights

Metering Rights

Password Rights

Question Rights

Main Menu Window

Admin Password

Administrative Proxy

Help - User Help Screen

Note - User Notes

Startup - Startup Programs

Menu Icons

DOS Environment Variables

DOS Program PIF Files

Admin Mode

User Mode

Upgrade Procedures

Registration Procedures

Required Files

Optional Files

Startup Options

Setup

Sub-menu Titles

NWCALLS.DLL

Network

Stand-alone

NetWare

WOmenu

DOSmenu Menu System

Rights


WOmenu Default Main Menu Picture

This menu screen, shown in Admin Mode, is configurable by you, the administrator.


Introduction

Welcome to Windows Office Menu (also known as WOmenu).

WOmenu was designed as a simple yet powerful menu system for both network and stand-alone environments where users must operate under Microsoft Windows.  Our environment demands a safe, secure menu to help our users run both DOS and Windows applications without allowing undue access to our large Texas-wide-area NetWare network.  The menu system we needed had to be both easy to use and flexible and yet it had to stay out of the way as much as possible for our user operations.  Because we could not find one, we wrote our own.  We hope it helps you control your Windows environment as well.

Please use WOmenu as you see fit, but if you continue to use it, you should register according to standard shareware policies.

Office Situation 1

Office Situation 2

Here is a quick overview of WOmenu:

Flexible user-specific menus based on one menu file.

Unlimited menu items.

Unlimited sub-menus.

Run any program, DOS or Windows based.

Prevent multiple runs of the same program.

Easily operate the menu system without having to outfit users with mice.

Many rights options to determine whether a menu item is usable by a user.

Works great with NetWare and any other network operating systems.  Also works well as a stand-alone system.

Complete user logging capabilities.

Complete Software Metering Services for applications run through WOmenu.

Works well in conjunction with our DOS-based network system, DOSmenu.


Office Situation 1

Here is one example of why you might need WOmenu to help you:

You have a network with one or more servers and many users.  Most of these users run a couple of business-specific applications and some utilities that you allow.  Now, you are finding that these users can be much more productive if they could run their one or two business applications at the same time while having their email and a utility or two instantly available.  This, of course, means multitasking, which probably means Windows.  But how do you keep all of those nice things that Windows offers, like the File Manager and games away from the users while defining a Program Group that makes sense to each user?

Enter WOmenu...it was made to solve just that!


Office Situation 2

Here is another example of why you might need WOmenu to help you:

Your network users are constantly calling you to add different items to their program menu groups.  They call because they can't find an items in a group.  They call because some of the items in their groups do not work for them.  They call because they have gotten "lost" in Windows.  Etc., etc.  You would really like to take control of the Windows environment of all your users and invent some way of being able to manage all of them from a single point of reference.

Again... WOmenu can help you!


Requirements

WOmenu requires Windows version 3.1 or greater.

WOmenu's only additional requirement is that it needs the Visual Basic 3.0 runtime library, VBRUN300.DLL, in order to run.  If you do not have this file yet, it may be downloaded from almost any on-line service.  We can also provide you with this program, if required (it is shipped with registered versions).

Required Files

Optional Files


Startup Options

WOmenu is normally started at user workstations by specifying WOMENU.EXE as the Windows shell.  The first line in their SYSTEM.INI should read

shell=[path]womenu.exe

However, it may be started directly from within Windows.  In this case, the command should be

[path]womenu.exe

Here, quitting WOmenu will not quit Windows.  This is how you, the administrator would run it.

Administration


Required Files

The following files are necessary to run WOmenu:

WOMENU.EXE

The Windows Office Menu program.

WOMENUS.EXE

The Windows Office Menu registration module.  After you have registered, this file is no longer needed.

WOMENU.INI

The Windows Office Menu initial initialization file.

WOMENU.WOM

The Windows Office Menu initial menu file.

MLIST.VBX

A Visual Basic library file for WOmenu.

VBCTL3D.VBX

Another Visual Basic library file for WOmenu.

CMDIALOG.VBX

Yet another Visual Basic library file for WOmenu.

COMMDLG.DLL

A Windows support file.

NWCALLS.DLL

A Windows NetWare support file (needed when using NetWare).

VBRUN300.DLL

The main Visual Basic runtime library.


Optional Files

WOMENU.HLP

A standard Windows help file (this file) for use in Admin Mode.  This file will never be seen by users in User Mode.

WOUSER.INI

This file holds user-specific options and is stored in the user's private Windows directory.  This file also holds the user's personal menu if allowed by the administrator.

WOMENU.LOG

(You choose name) If logging is enabled, this file is appended every time a user performs a menu action.  Included statistics are:  user name, node address, server name, date, time, and menu action.

WOMENU.MTR

(You choose name) If metering is enabled, this is the central file where the software metering information is kept.

WOMENU.CHG

(You choose name) If charging is enabled, this is the central file where the project charging  information is kept.

EMEDIT.VBX

Visual Basic library file for WOmenus WOedit File Editor (registered versions only).

DRAGDROP.VBX

Visual Basic library file for WOmenus WOedit File Editor (registered versions only).


Quick Start

To quickly get the menu system up and running, do the following (check the documentation later for specifics):

Shareware only:  Copy WOMNU.EXE to a work directory.

Shareware only:  Run WOMNU to extract the zipped files.

Run SETUP from Windows to install WOmenu.  The directory to install to should be your main Windows directory.  This directory is normally C:\WINDOWS on a stand-alone system and F:\WINDOWS on a network system.  To use WOmenu for all of your users, enter the Windows network directory.

If on a network, and the setup program did not copy place the WOmenu  files in your central shared Windows directory, you must move the following files there in order for all users to have access to the menu system:

WOMENU.EXE

WOMENUS.EXE (registration module)

WOMENU.HLP (for Admin Modehelp)

NWCALL.DLL (if on NetWare)

COMMDLG.DLL

CMDIALOG.VBX

VBCTL3D.VBX

MLIST.VBX

DRAGDROP.VBX (registered versions only)

EMEDIT.VBX (registered versions only)

Run WOMENU from the Windows directory.  This first run will make a default WOMENU.INI and WOMENU.WOM files in the same Windows directory.

That's all there is to it.  You now have an operational menu system.  You may use WOmenu's Admin Mode to change your program items and sub-menus as you desire.  After you get the menu the way you want it (especially if you administer a network) you will want to change some of the default setup options and add appropriate rights to the menu items so as to lock your users and protect your network.  This is accomplished with the Admin command.

If you plan to run in a networked multi-user environment, then check these sections out also:  DOS Environment Variables and Users Windows Environment.

Registered installations need to perform the registration procedure once.

Startup Options

Administration

Registration Procedures


Upgrade Procedures

There are two ways to upgrade your registered version of WOmenu.

Download From CIS (Or Other On-line Services)

You may download the latest shareware self-extracting ZIP file (WOMNU.EXE) anytime, run it, and then install its files over your existing registered files during installation.  You may then need to follow the registration instructions for registering your product as originally accomplished when you bought the product.  For those who own versions prior to 3.3, call Bremer Corporation for a registration number.  You are guaranteed free upgrades in this manner for at least two minor updates of the product.

By Mail Directly From Us

You may call or write to us and request the latest registered update.  Upgrade costs are $50 US for network versions and $25 US for single-user versions (both prices include shipping and handling).  This again guarantees you at least two more minor update upgrades.

Registration Procedures


Registration Procedures

To register your product, perform the following steps after installation:

Run WOMENU.

Press the Register button on the initial shareware screen.

Enter your registration number on the Register line.

Press Enter.

You will find your registration number on the Software License letter that was shipped to you along with your product.

You should only have to perform this procedure once.  However, if you upgrade the product at a later date with a newer version obtained from an on-line service or bulletin board service, you may need to perform this procedure again.

Therefore, you should keep your registration number in a safe place.  Your name and registration number is also kept on file at Bremer Corporation.

Please contact Bremer Corporation if you have problems with this procedure.

Upgrade Procedures


Commands - Admin Mode

The following commands are available to you, the administrator, while in Admin Mode:

NOTE: These commands may be accessed by pressing the first letter of the command button.

Help

Brings up a context sensitive help screen.  (Users never see this Windows help file in User Mode.)

Admin

Provides for complete menu system parameter setup by the administrator. (Users never see this command in User Mode.)

Edit

Allows editing of the highlighted program item or sub-menu item. (Users never see this command in User Mode.)

Move

Allows moving of the highlighted program item or sub-menu item within the same menu.  (Users never see this command in User Mode.)

Insert

Allows the insertion of a new program item or sub-menu item. (Users never see this command in User Mode.)

Delete

Allows the deletion of the highlighted program item or sub-menu item. (Users never see this command in User Mode.)

Back

Backs up to the previous menu if in a sub-menu.

Quit

Quits the menu system.  If WOmenu was started as the Windows shell, it will first check that all programs have been quit and then it will quit Windows as well.

F1

Brings up a context sensitive help screen. (Users never see this Windows help file in User Mode.)

F2

Toggles between Admin Mode and User Mode.  This command can (and definitely should be) be password-protected with the admin password.

F3

Allows the administrator to quickly run a program or utility.  This can even be done from a user's workstation if that user has system rights to the program you wish to run.  This command is password-protected with the admin password.

F4

Toggles between the main shared menu and the current users personal menu.  From here you can setup a personal menu for a user (or users).  Personal menus are kept in the user's private Windows directory (WOUSER.INI), so you must either add items to it from the user's workstation or by using the administrative proxy feature (F6) from your workstation.

F5

Refreshes (rereads) the INI and WOM files. The menu file is automatically reread every time a sub-menu is selected or deselected.

F6

Allows you to proxy (become) another user on the network as far as WOmenu is concerned.  This lets you check out another user's menu using their user ID and their group rights (on NetWare).  It is also a very convenient mode to use for setting up other user's personal menus from your admin workstation.  This command is password-protected with the admin password.

F7

Brings up an information dialog showing the highlighted menu items information. It is also available at the user workstation in User Mode.

F8

Brings up a workstation status screen.  It is also available at the user workstation in User Mode.

F9

Brings up the About screen. It is also available at the user workstation in User Mode.

Ctrl+X

Copies the highlighted menu item to the WOmenu copy buffer and then deletes the highlighted menu item from the current menu.  Users cannot use this command in User Mode.

Ctrl+C

Copies the highlighted menu item to the WOmenu copy buffer.  Users cannot use this command in User Mode.

Ctrl+V

Inserts the WOmenu copy buffer into the current menu.  Users cannot use this command in User Mode.

Ctrl+NumPad

Without a mouse, the NumPad keys along with the Ctrl key will move and resize the menu window.  The * key centers the window.

Administration

Commands - User Mode


Commands - User Mode

The following commands are available to users while in User Mode:

NOTE: These commands may be accessed by pressing the first letter of the command button.

Help

Brings up the a context sensitive help screen (but not this Windows help file).  If you have defined the optional User Help Screen, they will see that screen when at viewing the menu window.

Out

If activated, the Out button appears on user menu screens allowing the users to access their on-demand Out message protected screen saver.  This button/command can be disabled and hidden from users with the Admin command.

Note

If you have defined a note for some or all of the users, the Note button appears on those users' menu screens allowing them to re-read the note.  Remember, if they had not already seen the note during their current Windows session, or if you updated or changed it later, it will pop up automatically for them.

Goto

Allows users to select one of their already-running programs from a list.  This is basically a built-in task manager for the users.  Remember, it is a good idea to turn off the normal Windows Task Manager to disable the Ctrl+Esc key for users and help you have more control over their Windows environment.

Main

If the user has opened another menu file (via a menu item command), then the Main button will appear on their menu screen so that they may backup to the main menu at will.

Set

If you have allowed users to change their menu systems look, then this button will allow users to change their menu font and colors and save their menu windows size and position.  This button/command can be disabled and hidden from users with the Admin command.

NOTE:  This button does not show when the Main button is showing.

Per

If the user has a previously defined (by you) personal menu, then the Per button appears on their menu screen allowing them to toggle between the shared main menu and their personal menu.  Additionally, this command switches to Per when the user is actually in their personal menu.

Back

Backs up to the previous menu if in a sub-menu.

Quit

Quits the menu system.  If WOmenu is the Windows shell, it will first check that all programs have been quit and then it will quit Windows as well.  This button/command can be disabled and hidden from users with the Admin command.

F4

Allows the user to enter or change the active charge code.

Ctrl+NumPad

Without a mouse, the NumPad keys along with the Ctrl key will move and resize the menu window.  The * key centers the window.

Commands - Admin Mode


Admin Mode

Admin Mode is initially set as the default menu mode after installation as a convenience for you, the administrator, giving you full system editing capabilities.  In this mode you can define and setup all menu system interface, network, and support file options that are part of the Administration module.  Of course, this is also the mode used to setup actual menu items (and users personal menus, if desired).

While viewing the menu window in Admin Mode, you will see all menu items.  Those items for which you do not actually have rights are shown in red as information only (in User Mode you would not see them).

When finished with your system setup, and before allowing users into the menu system, you should define the admin password and then change the default mode to User Mode to protect your network environment.

Commands - Admin Mode

WOmenu Utilities (for optional WOUSER.EXE)


User Mode

User Mode is the normal operating mode for users.  In this mode, all menu rights are honored and users only see those menu items that the associated menu rights allow them to see.

Also, the User Mode help screens never mention anything having to do with Admin Mode functions.  In fact, users never see this Windows help file at all.

Remember, you can also employ the WOUSER.EXE file for your users, if desired, to guarantee User Mode startup and much smaller resource usage.  (registered versions only)

Commands - User Mode

WOmenu Utilities (for optional WOUSER.EXE)


Administration

WOmenu has one overall Admin command that leads to all menu setup functions with the exception of actual menu items.  All setup options are stored in the main WOMENU.INI file.  This following topics explain the different options.

Interface Options

Network Options

Support File Options

Startup - Startup Programs

Note - User Notes

User - User Help

Charge - Project Charging Service

See also:

Menu Items

Sub-Menu Titles

Menu Rights


Interface Options

User Mode

This is the normal default startup menu mode for users.  In this mode, users can only run the menu items that you determine through menu rights.  They never see any admin functions or admin help screens.  Once you have finished with your preliminary admin chores, set this mode as the default.  With registered versions, you should strongly consider using the WOUSER.EXE file as your users executable menu file instead of WOMENU.EXE.

Admin Mode

This mode is for initial admin chores.  Initially, WOmenu is set to start in this mode for ease of setup.  Once you have finished preliminary admin chores, and definitely before you allow users to use the menu, change the default mode to User Mode.  As an administrator, you may always return to this mode by simply pressing F2 and entering the admin password. Admin Mode has various help screens to guide you in setting up the menu properly for your users.

Admin Password

See Admin Password

Date And Time

This allows you to turn off the date and time display just above the menu list window.

Icons

This allows you to turn off the icon column in the menu list for your users, if desired.

Centered

Determines whether menu item text is centered or left aligned.

Grid Lines

Determines the visibility of the grid lines on the menu grid.

Descriptions

This allows you to turn off the menu description area just below the menu list window.  If on, this area automatically expands to up to two lines as necessary in an attempt to show the entire description.

"Out" Button

This determines whether users will be able to access the Out message function. This function is an on-demand screen saver with a user-determined message. They can use it when they will be away from their desk for any period of time to help protect their desktop.  It does not override any already installed Windows screen saver.

"Set" Button

This determines whether users will be able to set their own menu fonts and colors and save their menu window size and position.  If not, then they will always use the settings you choose.

NOTE:  The Set button does not show for users when they are not in the main menu file.

"Quit" Button

Enables the Quit button/command in User Mode.  If disabled, the user will not be able to directly quit WOmenu unless you place a /QUIT menu itemon the user's menu (and this item may still use menu rights).

NOTE:  When a user quits WOmenu, he/she is always asked first.  However, when another process sends a message to quit WOmenu, no questions are asked and the quit is immediate.  An example would be the Windows Task Manager end task option.

System Colors

Determines whether the menu system uses the current Windows system colors or the colors that you have setup.

Font (small button)

This is where you may define the main menu font.

NOTE:  Be sure all of your users have access to the font in their WINI.INI files!

Mnu Tx..(Colors) (small buttons)

This is where you can change the main menu colors.

NOTE:  Be sure your users have the capability of showing the colors that you choose.

Use "Running..." Form

This allows you to turn off the display of the Running... Program form that is usually shown while loading menu itemprograms.

Try For Alt INI File

This determines whether WOmenu will attempt to locate another main central INI file or not.

Use Activity Logging

This is used to activate user activity logging.  (Logging only works in User Mode).

Use Software Metering

This is used to activate software metering.  (Metering only works in User Mode).

Use Project Charging

This is used to activate project charging.  (Charging only works in User Mode).

Minimize On Item Run

If set, then WOmenu will always minimize itself prior to running a program item on the menu.

Save Window Position

You may move and resize the menu window while in Admin Mode to any startup position you wish for your users.  Use this to save that position.  This option does not remain checked.  The next time you enter the Administration screen, it will again be unchecked.  Check it only when you want to save the current menu window position.

Reset Position/Color/Font

If you get into trouble with the Window positioning or the menu colors or font changes, use this to reset them.  This item also will not remain checked.

Menu Title

This simply determines the title of the first, main menu window.

Message

If filled in, this message will be displayed unobtrusively at the bottom of the users' menu window (it does not show while in Admin Mode or with the shareware version). WOmenu looks for this text in the INI file every time the user changes window focus or runs an item.  So you may change it on the fly and know that users will soon see it.

Administration


Network Options

Attempt NW API Calls/Bindery Usage

This switch determines whether WOmenu tries to access the NWCALLS.DLL file to accomplish NetWare tasks (such as getting the user name and looking for the users groups).  Set this to no if not on NetWare so WOmenu will not issue error messages on startup.

Additionally, if you set this option to yes, and then later start Windows/ WOmenu without being logged in to a NetWare server, WOmenu will continue trying, behind the scenes, to activate your defined network functions as soon as you do obtain a login to a NetWare server during the current Windows session.

User/User Var

Here you determine whether you want NetWare or a login script DOS variable to determine the active user.  If on NetWare, use NetWare.  If not on NetWare, or if you develop problems with returned values from NetWare 4.x, use the DOS variable approach.

If using DOS variables, they should be set in the main login script.  See DOS Environment Variables for how to define this variable.

This function is only required if you plan to use the User or Group rights (see Menu Rights).

Server/Server Var

Here you determine whether you want NetWare or a login script DOS variable to determine the user's home server.  If on NetWare, use NetWare.  If not on NetWare, or if you develop problems with returned values from NetWare 4.x, use the DOS variable approach.

If using DOS variables, they should be set in the main login script.  See DOS Environment Variables for how to define this variable.

This function is only required if you plan to use the Server or Group rights (see Menu Rights).

Keep in mind that this server must be the actual server where users' groups are defined, if any.

Node/Node Var

Here you determine whether you want NetWare or a login script DOS variable to determine the user's workstation node address.  If on NetWare, use NetWare.  If not on NetWare, or if you develop problems with returned values from

NetWare 4.x, use the DOS variable approach.

If using DOS variables, they should be set in the main login script.  See DOS Environment Variables for how to define this variable.

This function is only required if you plan to use  Node right (see Menu Rights).

Groups

Here you decide whether you will activate the group right function.  For all NetWare 2.x and 3.x servers, this function works correctly.  It will only work correctly on 4.x if bindery emulation is turned on.

NOTE:  In each case above, the "...results" box will help you to decide if your environment will work with the appropriate switch.  On NetWare 2.x and 3.x, all functions should work fine.  On NetWare 4.x, the Group option may not work.

Allow NW Remaps

When using NetWare, WOmenu will save a drives mapping before it remaps the drive per the map right instructions.  Later, when the user quits the application that required the mapping, WOmenu will restore the original drive mapping for that drive if there indeed was an original mapping and if this option has been checked.

Allow NW Detachs

When using NetWare, WOmenu will attempt to attach to a server, if required, when performing a map command as directed by a map rights for a particular .  If an attachment was, in fact, required to perform the mapping, then WOmenu will later detach from that server once the user has finished with the application that required the mapping.  You can make WOmenu never detach from any server after a map command by unchecking this option.

Use NW Passwords

For the Out message function.  On NetWare, with SET ALLOW UNENCRYPTED PASSWORDS=ON (set at the file server), users will conveniently be able to use their NetWare password for their Out screen saver.  Otherwise, WOmenu will bring up dialog boxes to let them define their own (and this password will be saved encrypted to their private WOUSER.INI file).

NOTE:  In either password case above, you as the administrator will be able to "get in" to a user's desktop, if necessary, by issuing the overall admin password that you defined for the Admin Mode entry.

Administration


Support File Options

Alt INI File

If the Try Alt INI File option was checked and a filename is entered here, then WOmenu will continually try to find the alternate INI file that you specify while running.  If and when it does, it will switch to that INI file and use it for its menu setup specifications.

This option is meant for those situations when you have users that are running a local copy of WOmenu and then later attach/login to a server/location that has the central shared INI file that you want their system driven from.  This way, your User Notes and other functions will act centrally to all users as you need.

Keep in mind that when WOmenu switches to this second INI file, it will automatically run any Startup Programs that you defined in the file with the Admin command as long as the user is in User Mode.

Log File

The name of the log file to use, like f:\share\womenu.log.  Users must have write access to this file in order for logging to work on a network.  The log function logs menu start, menu end, and all program starts.  The user's login name (if defined), server (if defined), node address (if defined), date, and time name are all entered into the log file.  You may wish to periodically erase or archive this file because it can get quite large after a while if you have many users.  (Logging only works in User Mode).

Log File Max Size

If this is set to anything other than 0, WOmenu will automatically delete the log file when it reaches this size. You might wish to set a maximum size here to help keep your disk space under control.

Meter File

The name of the meter file to use, like f:\share\womenu.mtr.  Users must have write and erase access to this file in order for metering to work on a network.  See Software Metering Service for specifics on software metering.  (Metering only works in User Mode).

Charge File

The name of the charge file to use, like f:\share\womenu.chg.  Users must have write and erase access to this file in order for charging to work on a network.  See Project Charging Service for specifics on project charging.  (Charging only works in User Mode).

Charge File Max Size

If this is set to anything other than 0, WOmenu will automatically delete the charge file when it reaches this size. You should consider setting the maximum file size to 50000-100000 bytes.  Any larger size will cause a noticable delay for your users when charging is activated because WOmenu reads the entire charge file whenever an application is closed.

Administration


Startup - Startup Programs

Here you may add programs that should start automatically when the menu system starts for a user.  These programs can have menu rights that will determine for which users they will start as well.  This is an expanded substitute for the Windows Startup Group. WOmenu still honors any programs defined on the load= and run= lines of each user's private WIN.INI file.

If you enter a right for a startup program, then that program will only run if the user fits the rights that you outline.

You may also designate whether the program should run with a normal window or minimized.

If a complete command line is entered, then that drive/directory will become the current one as the program is run.

These programs are, of course, optional.

NOTE:  These programs will only actually run when WOmenu is the actual Windows shell program and it starts up in User Mode unless it is the users second INI file found with the Try Alt INI File admin option.

Administration

Menu Rights

Startup OptionsSupport Files


Note - User Notes

This is where you may define a note that will be seen by users starting the menu system.  While editing the note text, press Shift+Enter to enter a new line. A maximum of 4096 characters may be entered.  The note window's size and position is saved as well.  The note will only show between the dates that you enter.  This makes it convenient in that you do not have to remember to turn a note "off".  The note will also only show if the user has rights to the rights definition that you can optionally enter.

WOmenu holds a variable for each user to tell whether the note has been changed and let's the user's environment know whether it should re-display the note.  Therefore you can change the note on the fly and your users will soon see it, even if they are already in WOmenu.

If a note is available to a user, they will see a Note button at the bottom of their screen as well so that that they may review the note as needed.

NOTE:  Only the OK button is shown on this window in User Mode.

Administration

Menu Rights


Help - User Help Screen

You may define your own main help screen for your users here.  If filled in and activated, then users will see this screen when they press F1 or press the Help button from the menu screen.  A maximum of 4096 characters may be used for this purpose.  To enter a new line, press Shift+Enter.  You may also move and resize the help window as necessary for your users.

NOTE:  Only the OK button is shown on this window in User Mode.

Menu Rights


Menu Items

The following is offered to give you, as the administrator knowledge of the menu syntax used in menu files (like WOMENU.WOM).  Whenever possible, you should only make changes to this file through WOmenu itself.  However, if something goes awry, this will allow you to fix the problem.

The following explain the different sections of a defined menu line (the sections you edit with the Edit or Insert commands).

Item Title

Description

Program/Cmd

Work Directory

Window Title

Optional Rights

Run

Icon

NOTE: Versions after and including 3.6 use the | character (versus the , character) to separate the different items on a menu item line in menu files and any existing WOUSER.INI files.  If necessary, WOmenu will update an older menu file to the correct format and then add the line New Format=TRUE to the file.  Caution: If using an older file format (version prior to 3.6), update your system when all users are out of the menu and before letting them back in!

NOTE:  Versions after and including 3.7 use a separate menu file for menu items and all admin information is maintained in the INI file. If necessary, WOmenu will update an older file format to the correct format and then add the line New Files=TRUE to the INI file.  Caution: If using an older file format (version prior to 3.7), update your system when all users are out of the menu and before letting them back in!

[sub-menu titles]

These section headings define the sub-menus used in the menu system with the exception of the first one which is always labeled [Main Menu].  The following [...] sections, in fact, define the names of any and all sub-menus for the menu file.

Pgm#= (Pgm1, Pgm2, Pgm3, etc.)

These entries hold all information for each program item or sub-menu item.  The numbers define only the order of items on the menu.  In User Mode, only the items that pass the rights tests will be actually be shown.

The information is separated by the | character, so do not use that character in any of your menu item text fields.  Here are the sections:

Title| Window Title| Description| Program| Workdir| Icon File| Icon #| Rights

NOTES:

Not all sections must be filled out.  Although the title, program, and window title sections are always required for a program item, only the title section is required for a sub-menu item.  If you must edit the INI file yourself, be sure that the | characters remain to identify which section text belongs to, like:

Pgm1=&Microsoft Word|MICROSOFT WORD||winword.exe|||

Notice the missing description.  This is enough to run Microsoft Word if it exists and can be found in the path.

Sub-Menu Titles


Item Title

The item's button text, like &WordPerfect.  Use the & character to underscore a letter for a hotkey, if desired (use two &s to enter a & character).  For sub-menus, do not add the < {space} or {space} > to the title; WOmenu will handle this.

The item title can be anything you wish it to be; it has no significance to the menu system.

Menu Items


Description

The item's optional description text, like A Word Processor.

The description is optional and can be anything you wish it to be; it has no significance to the menu system.

Menu Items


Program/Cmd

The item's executable call to Windows and/or DOS, like f:\apps\wp\wp.exe.  This could be a PIF file or batch file as well.

Additionally, the program/cmd can signify a number of other types of events, as shown by the square-bulleted items below:

New Menu Item

Place /MENU at the beginning of the line to signify a jump to another menu, like:

/MENU f:\apps\newmenu.wom

When this command is selected, the user will be placed at the beginning of the new menu file.  A Main button will also be placed at the bottom of the user menu screen to allow the user to get back to the main menu file.

Quit WOmenu

Place /QUIT at the beginning of the line to signify quitting, like:

/QUIT

When this command is selected, the user will be asked if he/she wishes to quit (even from a sub-menu) just like when a user presses the Quit Button.  However, here the quit command can be protected with associated menu rights.

NOTE:  When a user quits WOmenu, he/she is always asked first.  However, when another process sends a message to quit WOmenu, no questions are asked and the quit is immediate.  An example would be the Windows Task Manager end task option.

Exit Windows, Run DOS App, Re-Enter Windows

Place /DOSRUN at the beginning of the line to signify quitting Windows, running a DOS application, and then re-entering Windows, like:

/DOSRUN dir f:\apps

or

/DOSRUN 123

When this type of item is selected, the user will not be asked about quitting (even from a sub-menu).  Instead, WOmenu will immediately cause Windows to quit (any running applications may ask questions during the quitting process which is a normal Windows function) and then run the application that you have defined.  When this application has finished, Windows will automatically restart and WOmenu will automatically re-appear (if it was the Windows shell program).

This feature is excellent for running those DOS-based applications that refuse to run under Windows.

NOTE:  This feature works best when WOmenu is the Windows shell program.

Attach And Drive Map (Or Just Map) To Another NetWare Server

Place /ATTACH at the beginning of the line to signify an attachment/mapping (or just a mapping) to another server and/or drive, like:

/ATTACH G~SERVER2/SYS:APPS

or

/ATTACH I~SERVERTWO/SYS01:

The syntax is just like that of the map right, sans the a= and the surrounding {}.  After performing this menu item, a message will be given to the user indicating the success of the operation.

Detach From Another NetWare Server

Place /DETACH at the beginning of the line to signify a detachment from another server, like:

/DETACH SERVER2

Program Parameters

Also, if you place a ? after the program command name (with nothing else on the command line after it) WOmenu will then pop up a question asking the user for an optional command line parameter for the command, such as a file name.  For example,

notepad?

or

notepad.exe ?

will ask the user for an optional text file name prior to running Notepad.

File Associations

If the file you wish to load is a standard filename that Windows knows about, either through the Windows registration database or in the [Desktop] section of the WIN.INI file, then that is all you have to enter.  WOmenu will associate the file with its parent program and run it appropriately.  For example,

WOMENU.HLP

will actually run

[PATH]WINHELP.EXE WOMENU.HLP

Running Programs With the Older Windows Exec Method

Although rare, you may have find necessity to use the older Windows 3.0 exec procedure to run a particular program.  If you think you have a need for this, simply place a # in front of the program/cmd line, like:

#MYOLDAPP app.txt

Keep in mind that file associations are not possible with this approach.

NOTE:  There is no program/cmd entry for sub-menu items.

Menu Items


Work Directory

The item's work directory, like h:\.

The work directory is an optional item.

NOTE:  There is no work directory entry for sub-menu items.

Menu Items


Window Title

THIS IS IMPORTANT. WOmenus software metering and project charging capabilities, server detaching, drive remapping,  and the preventing of allowing the user to run the same program twice at the same time -- all are somewhat dependent on the accuracy of this entry.

The actual name of the program's Windows title.  You may, if you desire, use the accompanying Run...Check button to run a program to check this one out.  Do not add any dynamically appended text here.  For instance, Notepad's Windows title in version 3.1 is Notepad.  But after loading a program, it becomes Notepad - [filename].  Make sure only to add the Notepad (or notep, for example) part here.  Case is not significant.  Another example:  for Winword 6, use Microsoft Word.  For PIF files, you will decide yourself what that Windows title will be in the PIF file entry -- just place it here as well -- and be sure they are unique from any other program's Windows titles that may be run from the users menu.

NOTE:  There is no work directory entry for sub-menu items.

Menu Items


Optional Rights

The item's optional rights to determine whether the user will get this item on their menu, like {d=f:\apps\wp}.  See Menu Rights for specifics on this powerful feature.

Menu Items


Run

This determines how a program will initially be displayed when it is run.  You may select normal, maximized or minimized.  This option cannot control the initial display of all programs (some control their own initial display).

Additionally, PIF files determine whether their applications will run maximized or not.  If not, you can still control whether they appear minimized to the user.

Menu Items


Sub-Menu Titles

Sub-menu titles are annotated slightly differently than normal program items.  Where &WordPerfect may define a program item, < &Word Processing > would define a sub-menu (and subsequent new section [Word Processing]). WOmenu takes care of this for you, but if you decide to edit your menu file manually, take this into consideration.  We strongly suggest that you DO NOT edit the INI file yourself -- use the Admin Mode commands to accomplish this.


Menu Rights

A powerful means of segregating the menu file between users is by applying the rights feature in User Mode.  You can decide what items should actually appear on a user's menu by defining certain rights for some or all of the items listed in the INI file.  You add these rights into the menu file with the Edit or Insert commands while in Admin Mode.  Let's discuss each right.

NOTE:  While in Admin Mode, you will always see all of the menu items, whether you, even as an administrator, have the rights for an item or not.  For example, if a menu item has a directory right of {d=h:\} and you do not have a mapped H drive, then you actually do not have rights to that item.  While in Admin Mode, this item will appear red on the menu screen as a reminder that that item is not available in your current network state.

NOTE: All example lines in the color blue in the topics below must be on one line in WOMENU.WOM.

All Rights {}

User Rights {u=}	Metering Rights {m=}

Node Rights {n=}	Password Rights {p=}

Server Rights {s=}	Question Rights {q=}

Group Rights {g=}	Group Rights (Faked) {d=}

Directory Rights {d=}	Map Rights {a=}

File Rights {f=}	Environment Rights {e=}

NOTES:

More than one of the above methods may be used at one time, either within the same right grouping or by having two or more groupings.  For example, you can place both a server (s=) and a group (u=) method on the same menu item, like:

Pgm1=&Notepad| NOTEPAD| Windows Notepad| notepad||| {u=joeb} {s=server1}

Here, it is read as user joeb AND on server1.

or by using the OR, ; such as

Pgm1=&Notepad| NOTEPAD| Windows Notepad| notepad||| {u=joeb;s=server1}

Here, it is read as user joeb OR on server1.

NOTE:  When using more than one grouping {}, each of the groupings must be true for the item to be shown (they are ANDed).  When using one or more methods within the same group, they are ORed.

Placing a ! before a name means not.  Where {u=joeb} means if the current user is joeb, then display the menu item; {u=!joeb} means display the item only if the current user is NOT joeb.  With some rights, such as the map (a=) right, the ! makes no sense and should not be used.

The biggest rule that you must remember about the rights methods are that within each set of braces {}, the answer must be true.  So if you use more than one set of braces for a menu item, they all must be true.  For example:

Pgm1=&Notepad| NOTEPAD| Windows Notepad| notepad||| {d=f:\apps\wp} {u=joe,jim;n=fa164505} {s=!server2}

will only show if the user can see directory F\APPS\WP AND the user is JOE OR JIM OR the node address is FA164505 AND the user is not on SERVER2.

Interface Options


All Rights

Right = no rights entered.  This method is the quickest and least secure way of checking users' rights because it checks nothing.  In other words, a menu item will show up on a user's menu, period.  Here, you will be relying on your defined network rights to determine whether a user will be able to run an item or not (they will see them on their menu).

Pgm1=&Notepad| NOTEPAD| Windows Notepad| notepad| h:\|||

User gets item if it is available, period, because the final section is empty.


User Rights

(May use the User Var definition)

Right = {u=user_id or u=user_id1,user_id2 ..}.  This method takes the discrimination down to the actual user ID running the system.  If the user name is in the list, then the user gets the item on their menu (if any other specified rights are also approved).

Pgm1=&Notepad| NOTEPAD| Windows Notepad| notepad| h:\||| {u=joeb}

User gets item only if his user login ID is JOEB.


Node Rights

(May use the Node Var definition)

Right = {n=node_address or n=node_address1, node_address2 ..}.  This method takes the discrimination down to the actual user's workstation.  If the node address is the same as that of the workstation, then the user gets the item on their menu (if any other specified rights are also approved).

Pgm1=&Notepad| NOTEPAD| Windows Notepad| notepad| h:\||| {n=fa164505}

User gets item only if his/her workstation's address is FA164505.


Server Rights

 (May use the Server Var definition)

Right = {s=server_name1 or s=server_name1,server_name2 ..}.  Here, by placing one or more server names with a menu item, you are saying only show this item when the user is logged into one of those servers.  Remember that if using NetWare to determine the user's server, WOmenu must be started from that server.  This option makes it easy to define one menu file for use on multiple Windows/server environments.

Pgm1=&Notepad| NOTEPAD| Windows Notepad| notepad| h:\||| {s=main_server}

User gets item only if the user is primarily logged into and running on MAIN_SERVER.


Group Rights

Right = {g=NetWare group name or g=NetWare group name1, group name2 ..}. WOmenu will look to see if any of the listed groups are part of the groups the user is a member of when it reads the menu file, and if the user is a member of none of them, it will not place the item on the user's menu.

This right only works on NetWare 2.x and 3.x and NetWare 4.x if bindery emulation is enabled.

Pgm1=&Notepad| NOTEPAD| Windows Notepad| notepad| h:\||| {g=everyone}

User gets item only if the user is a member of EVERYONE.


Directory Rights

Right = {d=directory name or d=directory name1,directory name2 ..}. WOmenu will look to see if any of the listed directories exist when it reads the menu file, and if none of them do, it will not place the item on the user's menu.

Pgm1=&Notepad| NOTEPAD| Windows Notepad| notepad| h:\||| {d=f:\apps\editor}

User gets item only if F:\APPS\EDITOR is visible in the user's environment.


Group Rights (Faked
Group Rights (Faked)

(How to fake this right on non- NetWare with bindery servers)

Right = --without NetWare, there is no such right--; use directory rights instead. WOmenu was built to be generic as far as networks are concerned.  Therefore, you can simulate group rights on non- NetWare environments by using the directory right instead.

Let's say you only want users who are a member of group WP or a member of group WORD_PROCESS to be able to run WordPerfect.  Within you networks admin facility, you should give each of these groups a trustee right assignment to a directory, like F:\FLAGS\WP in this case.  Read/file scan network rights are normally enough to see the directory.

Then, for the applicable menu item, define the following right:

Pgm1=&WordPerfect| WORDPERFECT FOR WINDOWS| A wordprocessor| f:\apps\wp\wp| h:\||| {d=f:\flags\wp}

which in effect will perform the same function as checking for a member of a group, because only those users who are a member of the actual group in question will be able to see this directory.  You could probably use {d=f:\apps\wp} here as well.

Another example:  for members of the ACCOUNTING group...

Pgm1=&Accounting package| GREAT PLAINS| Great Plains Accounting| f:\apps\gp\great.exe| h:\||| {d=f:\flags\gp}

or you could probably use {d=f:\apps\gp} here.


File Rights

Right = {f=file name or f=file name1,file name2 ..}. WOmenu will look to see if any of the listed files exist for the user when it reads the menu file, and if none of them do, it will not place the item on the user's menu.

Pgm1=&Notepad| NOTEPAD| Win Notepad| notepad| h:\||| {f=f:\windows\notepad.exe}

User gets item only if F:\WINDOWS\NOTEPAD.EXE is visible in the user's environment.


Environment Rights

Right = {e=dos_env_var~env_var_text, ..}.  This powerful right tests for the contents of any DOS variable.  For instance, to run a menu item depending on what room a person is in, set ROOM=room_number at login; then enter this right for the menu item in the menu file:  {e=room~102}  to test for room 102.

Pgm1=&Notepad| NOTEPAD| Windows Notepad| notepad| h:\||| {e=room~102}


Map Rights

(Not really a right)

Right = {a=drive_letter~server/volume:[directory]} (up to 3 maps - {} {} {}).  On NetWare, to run a program that requires specific directory structures, you can use this right to map the user's drive_letter to the server/volume:[directory].  This will happen just before the user runs the program.  This is not a restrictive right: it will not prevent the menu item from showing up on the user's menu.  It is a run right that facilitates the running of the program.

NOTES:

This right only works on NetWare environments.

The user should have been automatically attached to the server in question in the NetWare login script (if not, the user will be asked for their password to the server so an attachment can be performed).

The drive in question, should it already contain a mapping, will lose that mapping for this new mapping (do not map to critical map drives).

If a server attachment was required, then WOmenu will detach from the server soon after the user quits the program that required the attachment.  (WOmenu checks for unneeded attachments at various times, such as when the user runs another program or enters/leaves a sub-menu.)  This automatic detachment can be turned off with the Admin command.

If a server attachment was not required, then WOmenu will attempt to remap the drive to its original mapping, if any, soon after the user quits the program that required the attachment.  (WOmenu checks for needed remappings at various times, such as when the user runs another program or enters/leaves a sub-menu.)  This automatic remapping can be turned off with the Admin command.

This right is only effective with Windows-based programs.  For DOS-based programs, perform your mapping statements in the batch file that actually runs the program.

To map more than one drive at once (up to three), present the rights in their own separate sets, like: {} {} {}.

Pgm1=&OurPgm| OUR PROGRAM| Our Main App| g:\apps\ourpgm| h:\||| {a=g~acctg/sys:\apps}

Drive G will be mapped on server ACCTG, volume SYS to the \APPS directory.


Metering Rights

(Not really a right)

Right = {m=command[:number]}.  Entering this rule on an item's right line will force the command for the item to be metered, if metering is turned on and the meter file has been defined (within WOMENU.INI).  Please see the Software Metering Service for a complete discussion of this capability.

Pgm1=&Word| MICROSOFT WORD| Microsoft Word| winword.exe| h:\||| {m=winword:25}

This item will run as long as less than 25 other users are running it.


Password Rights

(Not really a right)

Right = {p=password where password is any alphanumeric, non-case sensitive, phrase}.  Placing a password on a menu item means that when the user selects this item, the user will be prompted for the correct password.  (This right is scrambled within the INI file).

Pgm1=&Notepad| NOTEPAD| Windows Notepad| notepad| h:\||| {p=restrict}

User gets item only if he or she can answer the password prompt with RESTRICT.


Question Rights

(Not really a right)

Right = {q=your question that demands a yes/no answer?}  This method simply pops up a question and asks for a Yes or No answer.  If no, it will not run.

Pgm1=&Notepad| NOTEPAD| Windows Notepad| notepad| h:\||| {q=Are you sure?}

Will only run if the user answers Yes.


Menu Icons

WOmenu allows you to place icons on your users' menu system.  This done while either inserting or editing a menu item.

Before the icon picture box are up to three radio buttons:

Original

The icon in force for the menu item before editing, if any.  This is available in case you decide to go back to your original icon but still want to save other changes to the menu item.

Default

WOmenu has default icons for sub-menu items, program items, quit items, new menu items, DOS run items, attach/map items, and detach items.

Program

If pressed, WOmenu will attempt to extract the first icon from the file name in the Program/Cmd text box.  If this program name has an extension, and is in the path or the full path name is given, and the file indeed has an icon, then WOmenu will find it.

After the icon picture box are two command buttons:

Save

You may save whatever icon is shown in the icon box (with the exception of the WOmenu default icons -- no need).  Although this is usually not necessary, the option is available when and if needed.  One time when it very well may be needed is if you define a program item with an executable file located on another server that the user is not automatically attached to.  In that case, you may wish to have the icon from that executable file located somewhere on the users home server.  After accomplishing an icon save, you will be asked whether you want to make the newly saved icon file the icon for the current menu item or not (it is not mandatory).

?

You may also use this button to pick an icon file or program containing icons.  In this case, if there is more than one icon in the file, you will then be able to browse all of them with the up/down slider bar tool.

When you press OK, whatever icon is shown in the icon picture box will be selected as the item's icon.

Menu Items


Users Windows Environment

The WOmenu system can make your users' Windows environment a simple one that is very easy to maintain.  We'll explain our setup as an example.

We set up Windows as a network install in F:\WINDOWS.  We ran one user setup from the Windows directory to get the default WIN.INI and SYSTEM.INI files.  We changed the shell defined in SYSTEM.INI to WOMENU.EXE.  Then we copied the necessary files to our own setup directory under F:\WINDOWS.  These files, surprisingly enough, consisted of only the following files:

WIN.COM

WIN.INI

SYSTEM.INI

NOTE:  No Program Manager files are needed at all.  If you want your users to have a screen saver, a particular screen background, etc., then set it up for this test user before copying these files to each user's Windows directory.

For each DOS program our users may run through their menu definitions, we defined a PIF file.  Our defined items in the INI (menu) file point to these PIF files on the Pgm#= lines.

To set up a user, we add them to a WINDOWS group in Syscon, make a directory under their private directory called WINDOWS, and copy the above listed files into that directory.

Our users run mostly DOS PIF-defined programs and have no need for a mouse. WOmenu runs and handles nicely without one.

Consider removing the Task Manager function from your users' Windows setup so that the Ctrl+Esc key will not confuse them.

That's all there is to it.  It's easy and quick to add/delete users from the menu setup.   And we have security while providing our users with true task switching.

DOS Program PIF Files

DOS Environment Variables


DOS Environment Variables

WOmenu can use up to three DOS variables to tell the system about your environment; user ID, server name and workstation node address.

In the case of NetWare, you probably do not need to define these variables.  However, to do so, define and load this DOS variable once during the main login script with the correct information.  This is, of course exactly what you want on non- NetWare environments.  The NetWare syntax is:

DOS SET USERID="%LOGIN_NAME"

where userid can be called anything you wish.  You could then add this name to various rights as desired. WOmenu takes care of the rest.

If you plan on using server name rights, then you would set up the server name variable in a similar manner.  The NetWare syntax (although probably not needed) is,

DOS SET SERVER="%FILE_SERVER"

place the above line in the users login script.

The node address variable is needed if you intend to restrict any menu items by comparing a work station's node address.  The NetWare syntax (although probably not needed) is:

DOS SET _NODE="%P_STATION"<<4

where the <<4 takes the first 4 numbers away from the actual twelve digit address, leaving the eight workstation numbers.


DOS Program PIF Files

When placing DOS programs on a user's menu system, there are a few cautions and guidelines we have learned and would like to pass on to you.  They are all optional but make a lot of sense toward keeping the menu usable and secure.

Make sure the entry for the Window title is the same as the entry you will enter for the item while in Admin Mode.  In this way, WOmenu will easily be able to find this program's DOS window when trying to determine if the user has already run the program once or not.  (WOmenu attempts to allow users only one run of each program on their menu.)

Recommend setting the option "Full Screen" to on.

Recommend setting the option "Background" to on.

Recommend locking out all "Shortcut Keys" except Alt+Tab (which is needed to switch between programs and back to the menu window).


Software Metering Service

WOmenu includes a powerful capability called software metering which enables you to control the number of simultaneous run instances of an application.  For instance, if you have bought 25 licenses for Microsoft Word, you now have the means to insure that only 25 copies are run at one time from with the menu system on your network.

There are more expensive and perhaps more foolproof offerings on the market for this service, but WOmenu does the job simply and easily.  And we believe that an administrator's effort level in attempting to control software licensing is at least 95% of any large distributor's concerns.

Here is how you set up metering:

Fill in these commands for the WOMENU.INI file with the Admin command:

Metering: checked

File: f:\share\womenu.mtr (or something like that)

Users must have WRITE and ERASE rights to the above area.

Place the meter right on those commands you want metered, for example:

Pgm1=&Word| MICROSOFT WORD| Windows word processing| f:\apps\word\winword.exe| h:\||| {m=word:25}

will meter the use of F:\APPS\WORD\WINWORD.EXE for all accesses from WOmenu.  Simply add this right to the menu item with the Edit command.  If 25 instances are already in use (in this example), then WOmenu will instruct the user that the maximum licenses are in use and to try again later.

The syntax is important.  The application keyword, in this case WORD, may be 10 or less characters with no spaces, followed by an immediate colon :, followed by an immediate number from 1 to 999 (with no spaces) -or- if no :number is entered, then 999 is assumed (good for counting accesses only).

These both work:

{m=word:25} ;limit 25

{m=word}    ;no limit

Of course anyone accessing WINWORD.EXE from outside of the menu system will not be metered in this way.  See WOmenu Utilities to find out how to meter DOS software runs from outside the menu system.  Also, if you call the application from more than one menu item in your menu file, make sure you place the same meter rights for each item.

NOTE:  (Metering only works in User Mode).

NOTE:  Recommend deleting the meter file periodically nightly...  f any user locks up while in a metered application, or gets rebooted at that point, then the meter count for that app will remain off by one (it will show one greater than actual).  For this reason, we recommend deleting the defined meter file periodically, perhaps at night before or after your backup.  See WOmenu Utilities for how to do this automatically.

Be careful when viewing your meter file.  The recommended way to view it is with WOmeter.


Insert Menu Item

Here you decide what type of menu item you wish to insert.  There are actually five types:

Program Item

A program for the user to run.

Or New Menu Item

A new menu file for the user to load.

Or Attach/Map Item

A server attachment and drive mapping (or just a drive mapping if already attached) for NetWare environments.

Or Quit Menu Item

An optional in-menu quit command for the user.

Sub-Menu Item

A sub-menu within the same menu file for the user to enter.

Program Manager Group Import

A specific Windows Program Manger group (or all groups).  In this case, a sub-menu item will be made and all items in the specified group will be placed under the sub-menu.  Please note that the Window title fields for these items will be ???.  If you desire to maintain the benefits of the Windows title feature, then edit the items and place the correct Windows title in each of them.

Menu Items


DOSmenu Menu System

We have another product called DOSmenu that is a network menuing system as well.  However, DOSmenu works from DOS.  It is a very popular product that can work nicely in conjunction with WOmenu.

DOSmenu allows even more menu rights than WOmenu and works great with NetWare and all other network systems.  It also functions nicely as a stand-alone product for single machines.

If you are interested in this product, please contact Bremer Corporation.  If you wish to try it first, it is available on CompuServe in its fully-functional shareware form.  Look in the NOVUSER/New Uploads (DL1) forum for the file DOSMNU.EXE.  It is also available on many BBS's worldwide.

Here are some sample screen dumps of DOSmenu:

DOSmenu Network Login Screen

DOSmenu Main Menu Screen

DOSmenu Main Help Screen

DOSmenu Workstation Status Screen


DOSmenu Network Login Screen

DOSmenu Menu System

DOSmenu Network Login Screen

DOSmenu Main Menu Screen

DOSmenu Main Help Screen

DOSmenu Workstation Status Screen


DOSmenu Main Menu Screen

DOSmenu Menu System

DOSmenu Network Login Screen

DOSmenu Main Menu Screen

DOSmenu Main Help Screen

DOSmenu Workstation Status Screen


DOSmenu Main Help Screen

DOSmenu Menu System

DOSmenu Network Login Screen

DOSmenu Main Menu Screen

DOSmenu Main Help Screen

DOSmenu Workstation Status Screen


DOSmenu Workstation Status Screen

DOSmenu Menu System

DOSmenu Network Login Screen

DOSmenu Main Menu Screen

DOSmenu Main Help Screen

DOSmenu Workstation Status Screen


Shareware

THIS IS NOT FREE SOFTWARE!  You may evaluate and use this product, but if you decide to make use of it on a regular basis, you must register your copy.

NOTE:  Businesses, government agencies and institutions are required to register this software package before extended use.

We offer several inducements to you for registering.

1	You will receive the most up-to-date copy of the program -- and we update the program on a regular basis.

2	We have additional mini-utilities that work nicely with WOmenu not included in this package that we will ship to you upon registration.

3	You will never see the shareware message again.

4	You will receive free technical support whenever you need it.

Make no mistake, however -- this is a fully functional version of WOmenu that is not "crippled" in any way.

Distribution

This is "user-supported" software.  You are hereby granted permission to distribute this evaluation copy of WOmenu and its documentation, subject to the following conditions:

Shareware WOmenu may be distributed freely without charge in evaluation form only.  The original PKZIP self-extracting file, WOMNU.EXE, is the preferred method.

WOmenu in its shareware form may not be sold, licensed, or a fee charged for its use.  If a fee is charged in connection with WOmenu, it must cover the cost of copying or dissemination only.  Such charges must be clearly identified as such by the originating party.  Under no circumstances may the purchaser be given the impression that he is buying a registered version of WOmenu.

Shareware WOmenu must be presented as a complete unit with documentation.  Neither WOmenu nor its documentation may be amended or altered in any way without permission of the copyright holder.

By granting you the right to distribute the evaluation form of WOmenu, you do not become the owner of WOmenu in any form.

Any other use, distribution or representation of WOmenu is expressly forbidden without written consent from the copyright holder.

Disclaimer

Bremer Corporation does not warrant that the functions contained in this program will meet your requirements or that the program operation will be uninterrupted or error free.

Bremer Corporation specifically disclaims all other warranties, expressed or implied, including but not limited to implied warranties of fitness for any particular purpose and of merchantability.

In no event will Bremer Corporation be liable to you for any damages, including but not limited to any lost profits, lost savings, commercial damage or other incidental or consequential damages arising out of the use or inability to use this program, or for any claim by any other party.

Trademarks

Trademarks of companies or products mentioned in WOmenu documentation files are the property of their respective companies.

Ordering Information

Registration Procedures

Upgrade Procedures

DOSmenu Menu System


Ordering Information

The non-commercial single-user registration fee for WOmenu is:

Per machine:	$45 US plus $10 S/H.

The commercial/government and multi-system site fee for WOmenu is:

Network environments:

Per server:	$195 US plus $10 S/H.

Non-network environments:

Per machine:	$45 US plus $10 S/H.

Send a check, money order or company P.O. for the appropriate amount to:

Bremer Corporation

3401 Cactus Wren Way

Austin, Texas 78746

We also accept Mastercard, Visa, American Express and Corporate American Express card telephone orders.

Thank you.

See WOORDER.DOC for a ready-made order form.

DOSmenu Menu System


Technical Support;Version
Technical Support

You can receive information and free technical support by contacting Bremer Corporation in one of four ways:

24-Hr Telephone: 512-328-2465

CompuServe Email: Skip Bremer - 71614,2556

Internet Email: zboray@io.com (orders only)

Internet Email: skipb@io.com (tech support)

NOTE:  The above 24-hour telephone number will at minimum give you a number where the author or another support staff person may be reached during business hours.

Ordering Information


Main Menu Window

 (NOTE:  Users never see this Windows help file in User Mode.)

You are presently in WOmenu's menu Admin Mode.  This mode is used to setup the menu system for all of your menu users.

Use the Admin command to setup overall parameters.  You should password protect this option!  Later, when the User Mode has been made the default, you, as the administrator, will be able to re-enter Admin Mode at any time by pressing F2 and then entering the admin password.

Use the Edit, Move, Insert and Delete commands to build the entire menu.  Keep in mind that you will see all items in this mode, whether available or not (due to any of your individual menu item rights).  Any item not available in your current situation is shown in red.

Use WOmenu's menu item buffer to help construct your menu.  Press Ctrl+C to copy a menu item, Ctrl+X to copy and delete a menu item, and Ctrl+V to paste the menu item in the buffer.

WOmenu was programmed so that your users' workstations do not need mice to run it.

Commands - Admin Mode


Administrative Proxy

This feature is accessed by pressing F6 while in Admin Mode.

Proxying as another user provides you, the administrator, with at two least two benefits:

1	One, you may view the menu system from another user's point of view. WOmenu will think it is the other user.  Therefore, any rights you have set in the menu file that depend upon the {U=user} and/or the {G=group} (on NetWare) rights will be displayed just as they would for that user.  Other rights are not affected (NetWare trustee rights are not switched to the new user).

2	Two, this is an excellent way to edit another user's personal menu from your admin workstation. WOmenu will read and write all personal menu changes to the user's WOMENU.INI and not yours.

Reason two above is why it is important that you set the correct private Windows directory when proxying. WOmenu will use that directory to find the user's personal menu file, WOUSER.INI.


Admin Password

The admin password, which is defined within administration, is very important to you, the administrator.

This password is required before allowing anyone into the menu Admin Mode.  You should define this password before allowing users access to WOmenu.  While users are in User Mode, they can only run the items that you want them to run on their menu.  But Admin Mode allows menu item changes and menu system parameter changes to be made (only if the user has write rights to the directory containing the WOMENU.INI file).  Therefore it is important to define and later use this password when you, the administrator, need to access menu administration.

This password also protects the F3 Administrative Run command, which allows you to run programs not on the menu from any workstation (as long as that workstation has network rights to the program).


Project Charging Service

WOmenu includes a powerful capability that allows you to track your program usage and apply it to different clients or projects.  This charging system logs all program usage to a particular charge code and then totals the usage for each application (as they are closed) in the charge log you define under administration.

For instance, if you have two clients that you would like to be able to charge by computer usage by your employees to, this service helps you do just that.

There are more expensive and perhaps more foolproof offerings on the market for this service, but WOmenu does the job simply and easily.  We believe the cost savings here could be well worth the benefit in most cases.

Here is how you set up the charging service:

1	Fill in these commands for the WOMENU.INI file with the Admin command:

Charging: checked

File: f:\share\charge.log (or something like that)

Users must have network WRITE and ERASE rights to the above area.

2	Add your charge codes to the text box on the Charge Codes screen.  These codes can be anything you wish as long as they are different from each other.  You can also decide how the actual workstation will be represented in the charge log file.  This is alos where you determine whether charging will be mandatory for your users or not.

Here is how your users use this service:

1	While in User Mode, a user presses F4 to bring up a list of charge codes and then picks one.  No programs may be open while this charge code selection/change process takes place.

2	Now, for every program the user runs, WOmenu will keep track of it and when finished with a program, WOmenu will log the total time spent in that program for the active charge code.  Multiple programs may be run and tracked at the same time.

NOTE:  The Window Title item that you define for your menu item applications is important as WOmenu uses this phrase as the "key" when it searches and tracks activity on running programs.

When a user who is actively charging (has a charge code selected) quits WOmenu, all programs must first be quit from within WOmenu so that accurate charge logging can be completed. WOmenu will remind the user if necessary.

Be careful when viewing your charge log file.  Use a utility, such as WOedit, that does not keep the file open.  Otherwise, user stations will not be able to write to it during the time you are viewing it which will lead to inaccurate charge totals.

You should consider setting the maximum file size (under administration) for the charge log file to 50-100K.  Any larger size will cause a noticable delay for your users when charging is activated because WOmenu reads the entire charge log file whenever an application is closed.

NOTE:  (Charging only works in User Mode).


WOmenu Utilities

WOUSER.EXE - Windows Office Menu (without administration modules)

This executable also runs the Windows Office Menu system, just like WOMENU.EXE, with a couple of important exceptions:

It contains no administration/setup overhead, making it approximately 100K smaller than WOMENU.EXE and allowing it to use much less system resources.

It always starts in User Mode (it cannot run Admin Mode) no matter how you have defined the initial startup mode to be.

Both WOMENU.EXE and WOUSER.EXE can be renamed, as necessary, and both of them may be run on the network at the same time.  The only requirement is that they both be in the same place so that they both use the same WOMENU.WOM and WOMENU.INI files.

This, then, can be the perfect file to use to give your users acces to Windows Office Menu.  (registered versions only)

WOCAL.EXE - WOmenu Calendar

A small calendar that easily works with the keyboard as well as a mouse.  (registered versions only)

WOCALC.EXE - WOmenu Calculator

A small calculator that works with the keyboard as well as a mouse.  (registered versions only)

WOEDIT.EXE - WOmenu File Editor

A powerful, multi-document file editor that edits files larger than 64K.  WOedit has many other features that make it a great system administration tool.  See the WOedit help screen for specific options.  (registered versions only)

WOERR.EXE - WOmenu Exit - Run - Restart

A Windows Exit - Run DOS Program - Restart Windows utility with the same functionality as the WOmenu internal /DOSRUN command.  It is a great tool for those programs that do not like to run Windows.  It has built-in command line capabilities as well.  See the WOerr help screen for specific options.  (registered versions only)

WOMETER.EXE - WOmenu Meter Viewer

A Windows real-time Software Meter Viewer/Reset utility.

This utility can optionally monitor your software usage from outside of the menu system but from within Windows.  All of your users' programs can be reliably monitored for metering.

There are no command line parameters; just run:

WOMETER

WOMETER.EXE will attempt to find the meter file's name in its WOMETER.INI file.  If it does not, it will make this file in its home directory and then you can fill in the name of the meter file, like:

[Setup]

Meter File=c:\windows\womenu.mtr (or something like that)

WOmeter allows real-time resetting of specific metered applications, in case the count has gone astray (perhaps from user lockups, etc.).

You may also set up WOmeter to automatically erase your meter file on a daily basis at a specified time.  The default is 00:01 (one minute after midnight).

You may also define the length of time WOmeter waits between re-reads of the meter file (between 10 and 60 seconds).

If you also use our DOS-based menu product, DOSmenu, WOmenu can easily work in concert with it for both meter files and log files.  Simply point the name and location of these files to the same files delineated in the DOSmenu INI file.  Then you will have a complete picture of your user activities on your network.

WOSS.SCR/EXE - WOmenu Screen Saver

A true screen saver that behaves similarly to the Out message function.  If you set this up for your users, consider adding a menu item that allows them to configure their screen saver without having to use the Windows Control Panel by accomplishing the following:

1	Copy WOSS.SCR to WOSS.EXE in the same shared Windows directory.

2	Enter this command as a menu item in the users' menu system:

WOSS.EXE /C

This allows WOss to be run as a program in the configuration mode.  (registered versions only)

WOVIEW.EXE - WOmenu File Viewer

A file viewer with a simple interface that works with the keyboard as well as a mouse.  It can view files larger than 64K and has a search capability.  This makes it a perfect utility for showing your users text files.  See the WOview help screen for specific options.


About

Windows Office Menu

(WOmenu)

Network Menuing System

Version 3.8d

Copyright © 1994,95

Bremer Corporation

All Rights Reserved

CompuServe Email: Skip Bremer - 71614,2556

Internet Email (orders): zboray@io.com

Internet Email (support): skipb@io.com

Internet FTP Download: ftp://ftp.io.com/pub/usr/zboray/shareware

Internet Web Home Page: http://www.io.com/~zboray/BremerCorp

Ordering Information

Registration Procedures

DOSmenu Menu System


NWCALLS.DLL

This file is required when operating on NetWare networks and utilizing any of the API/bindery functions defined in administration.  It should reside in the Windows network shared directory.


Network

An operating system that allows multiple computer workstations access to shared applications and utilities.  WOmenu is an example of a utility that can be shared on a network.  WOmenu also works well in a stand-alone environment.


Stand-alone

An environment where each computer workstation is an island unto itself.  Applications and utilities that are to be accessed by each computer workstation must physically reside on each workstation hard disk.  WOmenu is a utility that can operate in this environment as well as in a shared network environment.


NetWare

A popular network operating system by Novell, Inc.  NetWare typically operates on top of MS-DOS or PC-DOS.  When Windows is run in a NetWare environment, it is usually done so in a shared manner (all workstations run Windows from the network file server).  WOmenu works very well in this environment.


WOmenu

The short name for the Windows Office Menu Network Menuing System.


Rights

WOmenu uses Menu Rights to determine whether a menu item (either program or sub-menu) will appear on the user menus and therefore be accessible to that menu user.  This powerful feature allows you, the administrator, to make and maintain one overall menu for all of your users!

All Rights {}

User Rights {u=}	Metering Rights {m=}

Node Rights {n=}	Password Rights {p=}

Server Rights {s=}	Question Rights {q=}

Group Rights {g=}	Group Rights (Faked) {d=}

Directory Rights {d=}	Map Rights {a=}

File Rights {f=}	Environment Rights {e=}


Personal Menus

This is a powerful feature that allows users to have their own menu file.  A user gets a personal menu only if you add something to it from Admin Mode.  The administrative proxy feature lets you, the administrator, set up a users personal menu from your workstation, if desired.

Personal menus are useful for those commands that are very user-specific that you would rather not place in the main shared menu.

If a user has a personal menu, that user will then also have a Per button at the bottom of their menu window which enables them to toggle from the main menu to their personal menu and back again.

NOTE:  Users can only run items from their personal menu; they cannot edit them.


Window Title Entry

The Window title entry for a program menu item is important for the following reasons.

1	It prevents users from running a menu item more than once.

2	It is required for the Software Meter Service.

3	It is required for the Project Charging Service.

4	On NetWare, it provides a means of detaching from servers that were attached to solely in order to run a menu item.

5	On NetWare, it provides a means of remapping drives to their original mapping after being mapped solely in order to run a menu item.

If the above items are not important to you for a particular menu item, then enter anything bogus for the Window title, such as ? and do not worry about it.

Menu Items